## Introduction

In my last post from Scrum Artifacts series, I described the king of artifacts in Scrum framework - [Product Backlog](/blog/scrum-artifacts-1-product-backlog/). Today I would like to tell you more about the next artifact - Sprint Backlog. 


## What is Sprint Backlog?

If Product Backlog is a king or queen of the Scrum Artifacts, Sprint Backlog can be called their beloved child. 

Based on the Scrum Guide: 

> The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. 

## When & How the Sprint Backlog is created?

Sprint Backlog is created during the [Sprint Planning](/blog/scrum-events-2-sprint-planning/) session, when Scrum Team develops a plan for the Sprint and decides what can be "Done" during the upcoming iteration.

[Product Owner](/blog/scrum-roles-2-product-owner/) presents the business objectives and proposes Product Backlog items for the Sprint.

Then the Scrum Team starts discussion about functionalities and items that will be included in the Sprint.  Based on their expertise and skills, the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) should decide what items can be “Done” in the next iteration and what work is required in order to achieve it. That’s how the Sprint Backlog is formed. 

## Sprint Backlog - transparency & commitment

Sprint Backlog is a great tool in Scrum that promotes transparency and supports commitment. 
First of all, [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) selects by themselves all items that will be "Done" during the Sprint. They commit to the work and decide how it will be done. They also own the Sprint Backlog and are responsible for managing their workload. It helps them to be fully committed. 

What is more, having a clear understanding of what needs to be done during the Sprint, promotes Transparency and minimizes understatements. 

Based on the Scrum Guide: > The Sprint Backlog makes visible all the work that the Development Team identifies as necessary to meet the [Sprint Goal](/blog/sprint-goal-why-do-we-need-it/).

The [Development Team](/blog/scrum-roles-1-development-team/) can be fully focused on their work, which increases the value of developed increment. 

![Transparency](img/transparency.jpg)

## Sprint Backlog & Continuous Improvement

During [Sprint Retrospective](/blog/scrum-events-5-sprint-retrospective/), Scrum Team should select at least one improvement and include it in the Sprint Backlog.

That’s the best approach to make sure that improvements discussed on the [Sprint Retrospective](/blog/scrum-events-5-sprint-retrospective/) are part of the Sprint.  It will create continuous improvement and help the [Development Team](/blog/scrum-roles-1-development-team/)  to become a high performance team.

## Sprint Backlog - Fully prescribed?

Initially when Sprint Backlog is created it contains enough details to be understood by the  [Development Team](/blog/scrum-roles-1-development-team/).

Does it mean that it is fully described and fixed? Definitely no. It is modified by the [Development Team](/blog/scrum-roles-1-development-team/) and emerges during the Sprint.  The team can discover that they need to adjust the plan, do some additional tasks or change their approach. 

It is important to mention that Sprint Backlog solely belongs to the [Development Team](/blog/scrum-roles-1-development-team/). It means that Sprint Backlog can be changed but only if [Development Team](/blog/scrum-roles-1-development-team/) needs to update it. It cannot be updated by [Product Owner](/blog/scrum-roles-2-product-owner/) or [Scrum Master](/blog/scrum-roles-3-scrum-master/).

The [Development Team](/blog/scrum-roles-1-development-team/) is committed to the work and they decide what changes are required. They can add new work if it is required in order to achieve the Sprint Goal or remove tasks that are no longer required. 

## Sprint Backlog & Daily Progress

During the Sprint the [Development Team](/blog/scrum-roles-1-development-team/) is responsible for tracking their work progress.  Sprint Backlog helps them to track total remaining work and inspect it on Daily Scrum.

Transparency of all work required in the Sprint gives the team possibility to plan their work daily and adapt if there are any changes in tasks required or impediments to be removed. 

![Progress](img/progress.jpg)

## Summary

The most important information about Sprint Backlog that you should remember from this post: 
* It is set of Product Backlog items selected for the Sprint plus delivery plan 

* Sprint Backlog is created during the [Sprint Planning](/blog/scrum-events-2-sprint-planning/) session 

* It promotes transparency and supports commitment 

* During Sprint Retrospective, at least one improvement should be selected and included in the Sprint Backlog. 

* Sprint Backlog solely belongs to the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) 

* It can be adjusted during the Sprint by [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) 

* Sprint Backlog is a great tool for tracking of daily progress

What is Sprint Backlog? Who is responsible for managing it? How is it created? Jump in to find it out.

1 post tagged with #sprint backlog